SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
Go

Go static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your GO code

  • All rules 70
  • Vulnerability20
  • Bug7
  • Security Hotspot14
  • Code Smell29
 
Tags
    Impact
      Clean code attribute
        1. Hard-coded secrets are security-sensitive

           Security Hotspot
        2. Constructing arguments of system commands from user input is security-sensitive

           Security Hotspot
        3. Using publicly writable directories is security-sensitive

           Security Hotspot
        4. Using clear-text protocols is security-sensitive

           Security Hotspot
        5. Using weak hashing algorithms is security-sensitive

           Security Hotspot
        6. Delivering code in production with debug features activated is security-sensitive

           Security Hotspot
        7. Searching OS commands in PATH is security-sensitive

           Security Hotspot
        8. Creating cookies without the "HttpOnly" flag is security-sensitive

           Security Hotspot
        9. Setting loose POSIX file permissions is security-sensitive

           Security Hotspot
        10. Using pseudorandom number generators (PRNGs) is security-sensitive

           Security Hotspot
        11. Creating cookies without the "secure" flag is security-sensitive

           Security Hotspot
        12. Formatting SQL queries is security-sensitive

           Security Hotspot
        13. Hard-coded credentials are security-sensitive

           Security Hotspot
        14. Using hardcoded IP addresses is security-sensitive

           Security Hotspot

        Setting loose POSIX file permissions is security-sensitive

        consistency - conventional
        security
        Security Hotspot
        • cwe

        In Unix file system permissions, the "others" category refers to all users except the owner of the file system resource and the members of the group assigned to this resource.

        Granting permissions to this category can lead to unintended access to files or directories that could allow attackers to obtain sensitive information, disrupt services or elevate privileges.

        Ask Yourself Whether

        • The application is designed to be run on a multi-user environment.
        • Corresponding files and directories may contain confidential information.

        There is a risk if you answered yes to any of those questions.

        Recommended Secure Coding Practices

        The most restrictive possible permissions should be assigned to files and directories.

        Sensitive Code Example

        For Chmod() in the os package:

        import (
            "os"
        )
        
        func main() {
            err := os.Chmod("/tmp/fs", 0777) // Sensitive
            if err != nil {
                panic(err)
            }
        }
        

        For Umask() in the syscall package:

        import (
            "golang.org/x/sys/unix"
        )
        
        func main() {
            oldMask := unix.Umask(0) // Sensitive
        }
        

        Compliant Solution

        For Chmod() in the os package:

        import (
            "os"
        )
        
        func main() {
            err := os.Chmod("/tmp/fs", 0770)
            if err != nil {
                panic(err)
            }
        }
        

        For Umask() in the syscall package:

        import (
            "golang.org/x/sys/unix"
        )
        
        func main() {
            oldMask := unix.Umask(0007)
        }
        

        See

        • OWASP - Top 10 2021 Category A1 - Broken Access Control
        • OWASP - Top 10 2021 Category A4 - Insecure Design
        • OWASP - Top 10 2017 Category A5 - Broken Access Control
        • OWASP File Permission
        • CWE - CWE-732 - Incorrect Permission Assignment for Critical Resource
        • CWE - CWE-266 - Incorrect Privilege Assignment
        • STIG Viewer - Application Security and Development: V-222430 - The application must execute without excessive account permissions.
          Available In:
        • SonarQube IdeCatch issues on the fly,
          in your IDE
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube ServerAnalyze code in your
          on-premise CI

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use